Stream recognition and filtering

ABSTRACT

A method obtains a first data item signature for a first data item, the first data item signature comprising an association between a plurality of synch points in the first data item and a corresponding plurality of block signatures. The process attempts to find one of the synch points in a second data item; and, if such a synch point is found, then a block signature of a corresponding block of bits in the second data item is determined. The process ascertains whether the synch point and corresponding block signature from the second data item correspond to a synch point and block signature in the first data item. If a predetermined number of synch points and corresponding block signatures match, the first and second data items are considered to match. In response to said determining, one or more actions associated with the first data item are performed.

COPYRIGHT STATEMENT

This patent document contains material subject to copyright protection. The copyright owner has no objection to the reproduction of this patent document or any related materials in the files of the United States Patent and Trademark Office, but otherwise reserves all copyrights whatsoever.

BACKGROUND OF THE INVENTION

1. Related Applications

This application is a continuation-in-part (CIP) of co-pending U.S. patent application Ser. No. 14/452,465, titled “Stream Recognition And Filtering,” and filed Aug. 5, 2014, which is a continuation of PCT/US2013/026264, filed Feb. 15, 2013, which claims priority from U.S. provisional applications no. 61/607,021, filed Mar. 6, 2012 and No. 61/604,959, filed Feb. 29, 2012, the entire contents of each of which are hereby fully incorporated herein by reference for all purposes.

2. Field of the Invention

This invention relates to stream recognition and filtering.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects, features, and characteristics of the present invention as well as the methods of operation and functions of the related elements of structure, and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification.

FIG. 1( a) depicts a data stream;

FIG. 1( b) depicts a synch point and a corresponding block of bits;

FIG. 1( c) depicts a stream signature for the data stream of FIG. 1( a);

FIGS. 2( a)-2(d) depict processing of data streams according to exemplary embodiments hereof;

FIGS. 3( a)-3(b) show structures used to process multiple streams according to exemplary embodiments hereof;

FIGS. 4( a)-4(b) depict the processing of multiple streams according to exemplary embodiments hereof;

FIG. 5 shows exemplary data structures for processing streams according to exemplary embodiments hereof;

FIGS. 6( a)-6(c) show an example stream processed using the data structures of FIG. 5 according to exemplary embodiments hereof;

FIG. 7 shows a typical packet;

FIGS. 8(A)-8( c) show aspects of operation of match-triggered actions according to exemplary embodiments hereof; and

FIG. 9 is a schematic diagram of a computer system.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EXEMPLARY EMBODIMENTS Background and Overview

It is often useful and desirable to examine data being stored on devices or transmitted between devices (e.g., over a network) in order to try to determine whether or not the data correspond to other, known, data. For example, it may be useful or desirable to determine whether data stored on a device corresponds to or is a full or partial copy of other data. As another example, it may be useful or desirable to determine whether a data stream being sent between two devices corresponds to (or is a full or partial copy of) other data.

The inventors have realized that a determination that data being transmitted between devices corresponds to other, known, data may be used to trigger or initiate certain actions (e.g., blocking the data, replacing at least some of the data, billing for the data, etc.).

DESCRIPTION

A data stream (or stream) comprises a sequence of bits. The sequence of bits in a stream may represent or encode some kind of data item (e.g., a movie or an image or music, a data base, etc.). The sequence of bits in a stream may be encrypted and/or compressed. Those of skill in the art will realize and understand, upon reading this description, that the invention is not limited by what the underlying sequence of bits represent.

As used herein, data refers to any arbitrary data, regardless of what the underlying data represent and regardless of how the underlying data are formatted, encoded or stored.

U.S. patent application Ser. No. 14/452,465, from which the present application claims priority, describes, inter alia, systems, methods, and devices for determining whether two data items match each other, at least in part. The matching may be based on so-called synch points in the data items.

STREAM RECOGNITION

Exemplary stream recognition processes are described here, corresponding to those described in U.S. patent application Ser. No. 14/452.465. Those of ordinary skill in the art will realize and appreciate, upon reading this description, that the matching of two data items is not limited to the approach described in U.S. patent application Ser. No. 14/452,465, and that different and/or other approaches may be used, alone or in combinations.

With reference to FIGS. 1( a)-1(b), a stream 100 (a stream of bits) includes a plurality of synch points (in the drawing the stream is shown with i synch points, denoted SP₁, SP₂, SP₃, SP_(i), collectively referred to as SP_(j)).

Following each synch point in the stream is a block of bits (the j-th block being denoted B_(j) in the drawing).

As shown in FIG. 1( b), the i-th synch point (SP_(i)) consists of k bits (b₀b₁ . . . b_(k)), and the i-th block of bits (B_(i)) consists of j bits (c₀ . . . c_(j)).

While the j-th block of bits is shown in the drawing as immediately following the j-th synch point, it should be apparent that the j-th block of bits may be separated from the j-th synch point by some known amount.

In a presently preferred implementation there are sixteen (16) synch points, each consisting of 32 bits, and each block of bits consists of 256 bytes. In another implementation there are ten (10) synch points, each consisting of 64 bits, and each block of bits consists of 256 bytes. As used herein, the number of bits in a stream is referred to as the size of the stream, the number of bits in a synch point is referred to as the size of the synch point, and the number of bits in a block of bits is referred to as the size of the block of bits. Those of skill in the art will realize and understand, upon reading this description, that different and/or other numbers of synch points may be used than the number shown above, that a synch point may have a different size than that shown above, and that the block of bits may have a different size that the number shown above.

Those of skill in the art will realize and understand, upon reading this description, that the number of synch points may, in some cases, be determined as a function of the size of the stream of bits.

Corresponding to each block of bits B_(j), is a value H_(j) determined by applying a function (h) to the block of bits, so that:

H_(j)=h(B_(j))

The value H_(j) is also referred to herein as the block signature for the j-th block of bits.

The function h should have the following property: for any two arbitrary blocks of bits, B_(a) and B_(b), if B_(a) is equal to B_(b) then h(B_(a))=h(B_(b)).

Other desirably properties for the function h include that:

(a) a small change in B_(i) is likely to result in a different value of h(B_(i)); and

(b) the function h is relatively easy and quick to compute.

The function h may be, e.g., any hash function. In some implementations a message digest function such as MD5 or SHA-1 or the like may be used, although preferably a simpler and more lightweight function may be used. Preferably the hash function produces a 32-bit value.

Those of skill in the art will realize and understand, upon reading this description, that the function h need not (and likely will not) produce a unique value for every block of bits.

Each stream has a corresponding stream signature.

With reference now to FIGS. 1( a)-1(c), the signature of a stream with i synch points (SP₁, SP₂, SP₃, . . . SP_(i)) consists of the i pairs <SP_(j), h(B_(j))>, for j=1 . . . i. The diagram in FIG. 1( c) shows a logical representation of the signature 102 of the stream 100 of FIG. 1( a).

Creation of a stream signature for a data stream is described with reference to FIGS. 2( a) and 2(b). As shown in FIG. 2( a), a stream S is processed by an initial setup 200 to produce a stream signature 202. The processing by the initial setup 200 is described in greater detail with reference to the flowchart in FIG. 2( b). The initial setup process 200 will create a stream signature 202 consisting of a number (k) of pairs <SP_(j),h(B_(j))>, for j=1 k, for some value of k. The value of k is preferably preset (e.g., 10, 15, 20, etc.), though, as noted above, the value of k may also be determined as a function of the size of the stream S.

In processing the stream 200, the initial setup 202 may first determine the size of the stream S (at 204). This size information may be used, e.g., to determine the number (k) of synch points needed for this stream and/or the separation of synch points within the stream. As will become apparent upon reading this description, for any given stream (S), it is preferable to have the synch points distributed across the entire stream (S).

The process 202 then (at 206) determines the next (i-th) synch point (SP_(i)) in the stream S, and the corresponding block of bits (B_(i)). The value H(B_(i)) is determined for block of bits B_(i) (at 208), and the pair <SP_(j), H(B_(j))> is stored in the signature for the stream S (at 210). The function “H” computed at 208 corresponds to the function h described above and is preferably a message digest of hash function such as MD5 or SHA or the like.

The process 202 then determines (at 212) if sufficient <synch point, value>pairs have been determined for this stream S. If so, the stream's signature (SSig) is stored (at 214), otherwise the another synch point is determined (at 206). At the end of processing a stream (S), a stream signature (e.g., of the form shown in FIG. 1( c)) is produced and stored in association with the stream S).

As will be apparent to those of skill in the art, upon reading this description, the fact that two streams have identical stream signatures (as determined using the process described herein) does not necessarily imply that the two streams are identical. For example, a first stream may consist of millions of bits, while a stream signature may consist of only ten or twenty <synch point, block of bit value> pairs, where the synch points are randomly distributed across the stream and wherein each synch point uses only 128 bits and each block of bits uses only 512 bits. In this case, if a second stream has exactly the same <synch point, block of bit value> pairs then it may correspond to the first stream, but it may not. However, if the second stream does not have the same <synch point, block of bit value> pairs as the first stream then it does not correspond to the first stream.

The inventors realized that for some applications it may be sufficient to determine whether a data stream corresponds sufficiently to another known data stream. They realized that in some applications it may be sufficient to determine that two streams may be equal with some degree of certainty. Such information may be used to trigger more extensive (and possibly expensive) processing of the streams to determine correspondence or equality.

With reference now to FIG. 2( c), having determined and stored a signature (SSig) for a stream S, an arbitrary stream can be processed to determine if it corresponds sufficiently to the stream S. Stream S′ is provided to the compare process 216 (described below with reference to FIG. 2( d)), which uses the previously stored stream signature (SSig) to determine whether or not the input stream S′ corresponds to the stream S.

The compare process 216 determines (at 218) whether there is any more stream to process. If not then no match has been found and so the streams do not match. If there is more of the input stream to process then the process looks for a synch point (at 220). It should be appreciated that the process will look for any of the synch points (SP) in the stream signature SSig, and does not need to look for them in order. As will be apparent to those of skill in the art, upon reading this description, this allows the input stream to be processed in pieces or packets which may arrive at the compare process 216 out of order.

Having found a synch point (SP), the compare process 216 then finds the corresponding block of bits (B) associated with that synch point (at 220) and determines the signature H(B) for the block of bits B. Those of skill in the art will realize and understand, upon reading this description, that the function H used in the compare process 216 must be the same as the function that was used to generate the stream signatures.

Next (at 226) the pair <SP, H(B)> is compared to the corresponding pair for the synch point SP in the stream signature SSig. If the pair does not match (at 228) the remainder of the stream (if any) is processed (at 218, . . . ). On the other hand, if (at 228) the pair <SP, H(B)> does match the corresponding pair for the synch point SP in the stream signature SSig, then (at 230) the compare process 216 determines whether there have been sufficient pair matches to consider the streams to match. The test for “Sufficient matches” (at 230) may use a count of the number of matches in the stream so far and may use that count value to determine a percentage match of the <synch point, block signature> pairs for the stream signature. In some preferred implementations, a 70% match (e.g., seven out of ten matches) is considered sufficient matches to consider the streams matching (at 232). Those of skill in the art will realize and understand, upon reading this description, that the percentage match required (up to and including 100%) is a function of the accuracy required by the compare process. Since, as explained above, the compare process 216 may be used to trigger additional (and more costly comparisons) when a match is found (at 232), the person of skill in the art will know and understand how to trade off false positive matches (at 232) with the cost of subsequent processing of sufficiently matching streams.

Thus far we have described comparing and possibly matching an input stream (S′) to a single previously-processed stream (S). In some embodiments an input stream may be compared to more than one previously processed stream (e.g., to a library or database of previously processed streams).

The diagram in FIG. 3( a) shows a logical organization 300 of a plurality (k) of stream signatures, one stream signature for each of k streams 51, . . . Sk. Each of the stream signatures may be determined as described above with reference to FIGS. 2( a)-2(b).

A process of comparing an arbitrary input stream (S) to each of these k streams is now described with reference to FIGS. 3( a)-3(b) and 4(a)-4(b). The compare process for one stream compared to multiple possible streams may find synch points for multiple stream signatures in the input stream, and it may also find matching <synch point, hash value>pairs for more than one signature. In summary, the process preferably tracks the number of matching <synch point, hash value> pairs it finds for each of the k streams (S1 . . . Sk), and declares a match between the input stream S and the first of the k streams to sufficient matches (based on some predetermined threshold for sufficiency, as discussed above).

With reference to the flowchart in FIGS. 4( a)-4(b), if there is more of the stream S to process (at 400), processing continues (at 402) to look for a synch point (SP) in the stream S that corresponds to at least one of the synch points for one of the streams S1 . . . Sk. In the flowchart the streams S1 . . . Sk are referred to as a set of streams denoted S′. If no synch point is found (at 402), then processing continues (at 400) to process any remaining part of the input stream S. If (at 402) a synch point (SP) is found in the stream S corresponding to any of the streams S1 . . . Sk (i.e., the set of streams S′), then processing continues (at 404) to determine the corresponding signature H(B) for the block of bits B associated with the found synch point (SP).

Next (at 406), the signature pair <SP, H(B)> is compared to the signatures for all of the streams in S′ associated with the synch point SP (where SP is the synch point found in the stream S that corresponds to at least one of the synch points in at least one of the streams S1 . . . Sk; and H(B) is the signature of the block of bits B corresponding to the synch points SP). With reference again to FIG. 3( a), the stream signature for each of the streams S1 . . . Sk is stored and available to the process, so that the <synch point, signature> pairs may be checked.

If no matching signature pair is found for the pair <SP, H(B)> for any of the streams in S′ (at 408), then processing continues (at 400) to process any remaining part of the input stream S. If one or more matching pairs <SP, H(B)> are found (at 408), the processing continues (at 410), where the count for <SP, H(B)> pair for all matching streams in S′ is updated.

Once the counts are updated (in 410), the process determines (at 412) if any of the streams (S_(m)) in S′ has sufficient matching pairs. If it is determined (at 412) that no stream in S′ has sufficient matching pairs, then processing continues (at 400) to process any remaining part of the input stream S. If any stream S_(m) in S′ does have sufficient matching pairs, the processing is done (at 414) and the input stream S is considered to match the stream(s) which had sufficient matching pairs.

It should be appreciated that the process described above may result in the input stream S matching more than one stream in the set S′.

In some implementations, a data structure 302 (FIG. 3( b)) may maintain a checklist for each stream signature, so that the process may mark off (or check) each time a <synch point, signature> pair matches for that stream. That list allows the system to determine (e.g., count) the number of matching pairs for that stream. Those of skill in the art will realize and understand, upon reading this description, that the checklist may be implemented in any number of ways, including, e.g., as a bit map with one bit for each of the corresponding <synch point, signature> pairs. At the start of processing an input stream, all bits in the checklist are set to zero, and the corresponding bit values are set to one as matches are found. The sum of the bits in the bitmap checklist for a stream Sj will then give the number of matching pairs in the input stream for that stream Sj. As will be appreciated, different and/or other schemes may be used to track the number of matches.

Those of skill in the art will realize and understand, upon reading this description, that the use of the term “match” (or “matching”) with respect to two streams here does not necessarily imply that they are identical. Two streams may be said to match or correspond if a sufficient number or percentage of <synch point, signature> pairs for those streams are the same.

As previously discussed, those of skill in the art will realize and understand, upon reading this description, that different measures of sufficiency may be used to determine if two streams have sufficient matches. In some embodiments a 70% match will be considered sufficient, whereas in others higher matches (up to 100%) may be required. Those of skill in the art will realize and understand, upon reading this description, how to select a measure of matching sufficiency, based, e.g., on the application of the process and the tolerance for false positive matches. As noted earlier, in some applications, once two streams are found to match by the process described here, further tests may be used to determine if the streams match.

DATA STRUCTURES AND IMPLEMENTATIONS

Those of skill in the art will realize and understand, upon reading this description, that various optimizations may be applied to implementing the matching process. The data structures should preferably be:

Scalable: Should handle initially 100s to millions of entries with the option to grow if needed.

Memory efficient: Should use as little memory as possible

Search efficient: The search for a given pattern should not exceed O(n).

An exemplary data structure for implementations of the stream matching process is described with reference to FIG. 5. For this example, assume that each synch point is a sequence of six to eight bytes, and each fingerprint is a two-byte long value. Additional (optional) data may also be stored in the data structures. With reference to FIG. 5, the data structure (referred to as the Synch fingerprinting data structure (SFDS)) comprises of a set of arrays:

row 1—a 256-bit long array, where each bit corresponds to an ASCII code (to a code that can appear in a synch point)

row2—a 256² bits long array, with 256 bits related to each of the bits in row 1

row3—a 256³ bits long array, with 256 bits related to each of the bits in row3

row4—a list of trees that correspond to specific entries in row3

In an initialization process, pairs of synch points (a sequence of 6-8 bytes) and fingerprints (a 2 bytes long hash value with an additional optional set of data) are stored in the data structure as follows:

1. The 1st byte of the synch will set the relevant bit in row 1 (if it was not set yet).

2. The 2nd byte of the synch will set the relevant bit in the 256 bits of row2 that are related to the bit that was set in row 1 (if it was not set yet).

3. The 3rd byte of the synch will set the relevant bit in the 256 bits of row3 that are related with the bit that was set in row2 (if it wasn't set yet).

4. The rest of the synch bytes are stored in a tree that corresponds to the bit set at step 3. (The tree will be created if it did not already exist.)

5. The fingerprint and any additional data are connected to the relevant leaf of the tree from step 4 above.

EXAMPLE

The following example shows the use of the exemplary data structures described above (in FIG. 5). With reference now to the drawings in FIGS. 6( a)-6(c), consider a stream with the synch point SP1=“2, 254, 1, A, A, C” (the pattern is shown here in ASCII) with a corresponding fingerprint value 0×23a9. It will be appreciated that this means that the hash of the block of bits associated with the synch point SP1 is 0×23a9. For the sake of this example, assume that the stream has a stream id of 1000 and a synch index of 5.

This pair <“2, 254, 1, A, A, C”, 0×23a9> may be added to the data structure as follows:

1. The first character in the synch point is “2”, so set bit 2 in row 1 to 1

2. The second character in the synch point is 254, so set bit 254 of the 256 bits of row2 that correspond with bit 2 of row 1 to 1. That is, set row2[2][254] to 1.

3. The third character in the synch point is 1, so set the 1st bit of the 256 bits of row3 that correspond with the bit that was set in step 2. That is, set row3[2,254][1] to 1.

4. Assuming the bit that was set in step 3 already has a tree that corresponds with it and that tree already has an ‘A’ as a first character there is nothing to do with the ‘A’ (the fourth character in the synch point).

5. The fifth character in the synch point is also an ‘A’—add it to the tree as a second letter.

6. The sixth character in the synch point is a ‘C’, so add it to the tree as a third letter and create a new empty leaf bellow it.

7. Store the fingerprint value (0×23a9) and the additional data (Stream id 1000 and synch index 5) in a record and associate it with the leaf that was created in step 6.

Once the data structures are set up (as described above), an input stream can be processed, e.g., as described here with reference to FIGS. 6( a)-6(c). The matching process uses two auxiliary data structures, namely a Match Synch List (MSL) data structure (FIG. 6( b)) and a Match signature list of vectors (MSLoV) data structure (FIG. 6( c)).

The Match sync List (MSL) structure is a list with up to n entries (where n is the length of a synch). In this example the synch length is eight and the MSL has eight entries. The list holds the addresses (SFDS, FIG. 5) of the synchs that are being processed. Entry i of the vector holds the address of a synch for which the first i bytes matched a synch in the SFDS and its (i+1)th byte was not yet compared. A value of −1 stands for “no match” in that length.

The Match signature list of vectors (MSLoV) structure is a list of vectors. Each vector in the MSLoV list holds the list of synchs that match synchs of a given stream and the stream id of that stream. The j^(th) entry of the vector holds the synch index (taken from the SFDS) of the j^(th) synch found to be matching a synch of that stream.

The search flow using these data structures is as follows:

1. Each time a new packet is read, all the bytes in that packet are scanned byte by byte. Each byte is compared with the bytes in row 1 of the SFDS. If there is a match then entry 1 of MSL is set to the section of SFDS's row2 that relates to the relevant entry in SFDS's row 1.

2. A byte that follows a byte that had a match is compared several times. Assuming the previous byte is the i-th in a match then the current byte will be checked i times (the checks are done in the reverse order of the following description. That is first the check in step e is done, then the check in d, then . . . and the final one is the one described in step a):

a. As the first in a match (as described in step 1)

b. As a second byte in a match starting with the partial synch pointed by entry 1 of the MSL—the match is checked against the relevant section of SFDS's row2 that is pointed by MSL's entry 1. If a match is found than entry 1 is set to “−1” and entry 2 is updated with the address of the partial match found so far (that is the relevant entry in SFDS's row2).

c. As a third byte in a match starting with the partial synch pointed by entry 2 of the MSL—the match is checked against the relevant section of SFDS's row3 that pointed by MSL's entry 1. If a match is found than entry 2 is set to “−1” and entry 3 is updated with the address of the partial match found so far (that is the relevant entry in SFDS's row2)

d. . . .

e. As the ith byte in a match starting with the partial synch pointed by entry i-1 of the MSL—the match is checked against the relevant section of SFDS that is pointed by MSL's entry i-1. If a match is found than entry i-1 is set to “−1” and entry i is updated with the address of the partial match found so far (that is the relevant entry in SFDS)

3. Each time a full synch found (that is i in step 2 equals the length of a full synch and step 2.e is successful), the fingerprint is calculated. The calculated fingerprint is compared with the fingerprint pointed by SFDF's tree leaves that are pointed by the SFDF section in MSL's last entry. If a matching fingerprint is found then its stream Id and Synch Index are taken and MSLoV is updated:

a. If MSLoV does not have a vector for that stream Id then a new one is created and added to the beginning of MSLov. The Stream Id of the new vector is set to the stream Id that was taken from SFDS. Entry 1 of the new vector is set to Synch Index that was taken from SFDS.

b. If MSLoV already has a vector for that stream Id then it's first vacant entry is set to Synch Index that was taken from SFDS.

c. Note that if the matching synch has several leaves in MSLoV that steps a/b above are done separately for each of these leaves.

4. Once the number of indexes in a MSLoV vector exceeds a given amount (e.g., 8 out of 10) a match between the input flow and the stream which id is stored by the stream Id of that vector is defined.

5. Note that only an portion with a predefined length of the flow is searched for Synchs. If the search exceeds that portion with identifying a matching stream it is assumed to be an unknown stream and both MSL and MSLoV are cleared.

End Example

Those of skill in the art will realize and understand, upon reading this description, that different and/or other data structures may be used to implement the processes described here. It should be appreciated that some efficiency is preferred with respect to the data structures used. As objective, the data structure should store up to 1 million synch points (6-8 bytes each) with the fingerprints related to each of the synch patterns. As noted, the data structure is preferably created off line ahead of time (it will be prepared for an initial set of data and then updated incrementally whenever needed) while the search itself will be done in real time.

Using the data structures described in the example above (FIGS. 6( a)-6(c)), for one million synch entries:

The first 3bytes will be added to 3 lines each of 256 entries (3 times 2⁸ equal 2²⁴ equal to 16 million entries). The next bytes will be unique added to the last row of each prefix (less than 1% will have the same prefix and a list structure will be efficient enough, if not, a different synch pattern may be considered for the new added stream).

Adding a new synch is done off line and its in order of the synch length

Searching for a synch in the data structure can be done real time and is in the order of the synch length O(1).

Packetized Data Streams

In some cases the input stream of data may be in the form of packetized data. This may occur, for example, if the comparison processing is taking place in a device such as a router. In such cases, the device performing the processing may need to buffer payload data from more than one packet in order to perform the processing.

As is well known, in a packet-based network (such as a TCP/IP network, e.g., the Internet) data to be sent from one location to another are packetized (split into multiple packets). With reference to FIG. 7, a typical packet includes address information and payload. The payload comprises the data to be transmitted, and the address information includes information that allows the network to route the packet to its destination. Those of skill in the art will realize and understand, upon reading this description, that many forms of packetizing may be used, and the form and type of packets are not limiting to the invention. In addition, it should be appreciated that some networks may use multiple levels of protocols, so that a payload may itself be a packet that includes other address information. Regardless of the protocol(s) used, those of skill in the art will know how to extract data corresponding to a data item from a particular packet.

If the kind of packetizing is known in advance, it is preferable to select synch points such that each synch point fits within the payload of a single packet. However, since this may not be possible, it may be necessary to obtain and buffer the payloads of multiple sequential packets in order to perform the processing described above (looking for synch points and then processing their corresponding blocks of bits).

Those of skill in the art will realize and understand, upon reading this description, that the process and system described supports a comparison between two content streams much faster and in a more efficient way comparing to currently used approaches. In addition, the approach described herein can handle encrypted contents.

MATCH-TRIGGERED ACTIONS

As noted above, the inventors have realized that a determination that data being transmitted between devices corresponds to other, known, data may be used to trigger or initiate certain actions (e.g., blocking the data, replacing at least some of the data, billing for the data, etc.). The action(s) triggered by a match between a stream of data and a known data item may be performed on a device that determines the match and/or on one or more other device.

With reference to FIG. 8( a), each stream may have one or more match actions associated therewith. Thus, e.g., stream S1 with stream S1 signature has stream S1 action(s) associated therewith. It should be appreciated that the system is not limited by manner in which the actions are specified or by the order in which they take place (in the case of one or more actions). However, in some exemplary embodiments hereof an ordering may be applied to multiple actions.

In operation, as shown, e.g., in FIG. 8( b), a stream S is compared (at 802) to one or more other streams (e.g., using the signature matching techniques described above). If the stream S matches or corresponds to any of the other streams (e.g., based on their signatures), then the action(s) associated with the matching stream are performed. If two or more streams match the input then the actions associated with one of them (e.g., selected arbitrarily) will be performed.

With reference to the flowchart in FIG. 8( c), exemplary processing occurs as follows: while there is more of stream S (the input stream) to be processed, determine (at 806) if the input stream S corresponds to any of the streams in a library or database of streams. If there is a match or correspondence, then (at 808) perform the action(s) associated with a matching stream. If there is no match or correspondence between the input stream S and any other stream in the database or library of streams (as determined at 806), then determine (at 804) if there is more of the input stream S to be processed. If there is no more of stream S to be processed, then the streams do not match, otherwise continue to look for a match.

In some cases the default action for a non-matching stream may be to simply pass the stream through. In other cases some other action may occur for non-matching streams (e.g., recording a signature of a non-matching stream for a subsequent audit).

Exemplary actions that may be associated with a match may include one or more of:

Stopping the stream;

Modifying some or all of the stream; and

Tracking information about the stream (e.g., date, time, source, destination), e.g., for billing and/or auditing purposes.

As should be appreciated, modifying all of the stream is effectively replacing the stream with another stream. Modifying the stream may include inserting information into the stream, changing information in the stream, or removing information from the stream.

In some cases the stream may be modified in such a way that its synch points and their corresponding block signatures do not change.

Those of ordinary skill in the art will realize and appreciate, upon reading this description, that different and/or other actions may be taken when a stream matches.

Some actions associated with a stream may occur in real time, on the stream itself Some actions associated with a stream may be delayed or batched (e.g., billing actions).

Real Time

As used herein, the term “real time” means near real time or sufficiently real time. It should be appreciated that there are inherent delays built in to networks and devices (e.g., based on network traffic and distances), and these delays may cause delays in data reaching various components Inherent delays in the system do not change the real-time nature of the data or an application or process. In some cases, the term “real-time” may refer to data obtained or processing occurring in sufficient time to make the data or processing useful or usable. Furthermore, although the term “real time” has been used here, it should be appreciated that the system is not limited by this term or by how much time is actually taken. In some cases, real time computation may refer to an online computation, i.e., a computation which produces its answer(s) as data arrive, and generally keeps up with continuously arriving data. The term “online” computation is compared to an “offline” or “batch” computation.

Stream Selection

The analysis of streams may occur for some or all streams passing through a node (e.g., a router, a computing device, etc.). In some cases it may be useful to selectively examine streams to determine if they should be subject to further testing and evaluation. Several stages of filtering of streams may be applied, e.g.:

1. By communication protocol (e.g., HTTP, Bit torrent, etc.): the protocol being used may be ascertained and used to determine whether or not to do additional processing of the stream (for signatures, etc.)

2. By application protocol (e.g., MIME type): streams may be selected for additional processing based on information in the application protocol level.

3. Source/destination filtering: streams may be selected for additional processing based on their source and/or destination.

These exemplary pre-filtering approaches are listed as examples, and those of ordinary skill in the art will realize and appreciate, upon reading this description, that different and/or other techniques may be used.

COMPUTING

Programs that implement such methods (as well as other types of data) may be stored and transmitted using a variety of media (e.g., computer readable media) in a number of manners. Hard-wired circuitry or custom hardware may be used in place of, or in combination with, some or all of the software instructions that can implement the processes of various embodiments. Thus, various combinations of hardware and software may be used instead of software only.

FIG. 9 is a schematic diagram of a computer system 900 upon which embodiments of the present disclosure may be implemented and carried out.

According to the present example, the computer system 900 includes a bus 901 (i.e., interconnect), at least one processor 902, at least one communications port 903, a main memory 904, a removable storage media 905, a read-only memory 906, and a mass storage 907.

Processor(s) 902 can be any known processor, such as, but not limited to, an Intel® Itanium® or Itanium 2® processor(s), AMD® Opteron® or Athlon MP® processor(s), or Motorola® lines of processors, and the like. Communications port(s) 903 can be any of an RS-232 port for use with a modem based dial-up connection, a 10/100 Ethernet port, a Gigabit port using copper or fiber, or a USB port, and the like. Communications port(s) 903 may be chosen depending on a network such as a Local Area Network (LAN), a Wide Area Network (WAN), a CDN, or any network to which the computer system 900 connects. The computer system 900 may be in communication with peripheral devices (e.g., display screen 930, input device(s) 916) via Input/Output (I/O) port 909.

Main memory 904 can be Random Access Memory (RAM), or any other dynamic storage device(s) commonly known in the art. Read-only memory 906 can be any static storage device(s) such as Programmable Read-Only Memory (PROM) chips for storing static information such as instructions for processor 902. Mass storage 907 can be used to store information and instructions. For example, hard disks such as the Adaptec® family of Small Computer Serial Interface (SCSI) drives, an optical disc, an array of disks such as Redundant Array of Independent Disks (RAID), such as the Adaptec® family of RAID drives, or any other mass storage devices may be used.

Bus 901 communicatively couples processor(s) 902 with the other memory, storage and communications blocks. Bus 901 can be a PCI/PCI-X, SCSI, a Universal Serial Bus (USB) based system bus (or other) depending on the storage devices used, and the like. Removable storage media 905 can be any kind of external hard-drives, floppy drives, IOMEGA® Zip Drives, Compact Disc-Read Only Memory (CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Video Disk-Read Only Memory (DVD-ROM), etc.

Embodiments herein may be provided as a computer program product, which may include a machine-readable medium having stored thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. As used herein, the term “machine-readable medium” refers to any medium, a plurality of the same, or a combination of different media, which participate in providing data (e.g., instructions, data structures) which may be read by a computer, a processor or a like device. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks and other persistent memory. Volatile media include dynamic random access memory, which typically constitutes the main memory of the computer. Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor. Transmission media may include or convey acoustic waves, light waves and electromagnetic emissions, such as those generated during radio frequency (RF) and infrared (IR) data communications.

The machine-readable medium may include, but is not limited to, floppy diskettes, optical discs, CD-ROMs, magneto-optical disks, ROMs, RAMs, erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions. Moreover, embodiments herein may also be downloaded as a computer program product, wherein the program may be transferred from a remote computer to a requesting computer by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., modem or network connection).

Various forms of computer readable media may be involved in carrying data (e.g. sequences of instructions) to a processor. For example, data may be (i) delivered from RAM to a processor; (ii) carried over a wireless transmission medium; (iii) formatted and/or transmitted according to numerous formats, standards or protocols; and/or (iv) encrypted in any of a variety of ways well known in the art.

A computer-readable medium can store (in any appropriate format) those program elements which are appropriate to perform the methods.

As shown, main memory 904 is encoded with application 950-1 that supports the functionality as discussed herein (the application 950-1 may be, e.g., the initial setup 200 or the compare application 216). Application 950-1 (and/or other resources as described herein) can be embodied as software code such as data and/or logic instructions (e.g., code stored in the memory or on another computer readable medium such as a disk) that supports processing functionality according to different embodiments described herein.

During operation of one embodiment, processor(s) 902 accesses main memory 904 via the use of bus 901 in order to launch, run, execute, interpret or otherwise perform the logic instructions of the application 950-1. Execution of application 950-1 produces processing functionality in process 950-2. In other words, the process 950-2 represents one or more portions of the application 950-1 performing within or upon the processor(s) 902 in the computer system 900.

It should be noted that, in addition to the process 950-2 that carries out operations as discussed herein, other embodiments herein include the application 950-1 itself (i.e., the un-executed or non-performing logic instructions and/or data). The application 950-1 may be stored on a computer readable medium (e.g., a repository) such as a disk, hard disk or in an optical medium. According to other embodiments, the application 950-1 can also be stored in a memory type system such as in firmware, read only memory (ROM), or, as in this example, as executable code within the main memory 904 (e.g., within Random Access Memory or RAM). For example, application 950-1 may also be stored in removable storage media 905, read-only memory 906, and/or mass storage device 907.

Example functionality supported by computer system 900 and, more particularly, functionality associated with application 950-1 is discussed above with reference to FIGS. 2( a)-2(d) and 4(a)-4(b).

Those skilled in the art will understand that the computer system 900 can include other processes and/or software and hardware components, such as an operating system that controls allocation and use of hardware resources.

As discussed herein, embodiments of the present invention include various steps or operations. A variety of these steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the operations. Alternatively, the steps may be performed by a combination of hardware, software, and/or firmware. The term “module” refers to a self-contained functional component, which can include hardware, software, firmware or any combination thereof.

One of ordinary skill in the art will readily appreciate and understand, upon reading this description, that embodiments of an apparatus may include a computer/computing device operable to perform some (but not necessarily all) of the described process.

Embodiments of a computer-readable medium storing a program or data structure include a computer-readable medium storing a program that, when executed, can cause a processor to perform some (but not necessarily all) of the described process.

Where a process is described herein, those of skill in the art will appreciate that the process may operate without any user intervention. In another embodiment, the process includes some human intervention (e.g., a step is performed by or with the assistance of a human).

It should be appreciated that the words “first” and “second” in the claims are used to distinguish or identify, and not to show a serial or numerical limitation. Similarly, the use of letter or numerical labels (such as “(a)”, “(b)”, and the like) are used to help distinguish and/or identify, and not to show any serial or numerical limitation or ordering.

While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. 

We claim:
 1. A computer-implemented method, implemented by hardware in combination with software, the method comprising: (A) obtaining a first data item signature for a first data item, the first data item signature comprising an association between a plurality of synch points in the first data item and a corresponding plurality of block signatures, and associating at least one action with said first data item; (B) attempting to find a synch point of the plurality of synch points in a second data item; and (C) if a synch point of the plurality of synch points is found in the second data item, then: (C)(1) determining a block signature of a corresponding block of bits in the second data item, wherein the block signature is determined by applying a hash function or message digest function to the corresponding block of bits in the second data item; and (C)(2) ascertaining whether or not the synch point and the corresponding block signature from the second data item correspond to a synch point and block signature in the first data item signature; and (C)(3) when the synch point and the corresponding block signature from the second data item correspond to a synch point and block signature in the first data item signature, maintaining information indicative of the correspondence; (D) repeating steps (B) and (C) while at least some of the second data item remains unprocessed, until a predetermined number of synch points and corresponding block signatures from the second data item match synch points and corresponding block signatures in the first data item signature; (E) determining a match between the first data item and the second data item when the predetermined number of synch points and corresponding block signatures from the second data item match synch points and corresponding block signatures in the first data item signature; and (F) in response to said determining a match in (E), performing one or more actions of said at least one action associated with the first data item.
 2. The method of claim 1 wherein steps (B) and (C) are repeated in parallel for multiple different portions of the second data item.
 3. The method of claim 1 wherein at least one of said one or more actions associated with the first data item are selected from: (F)(1) denying access to the second data item. (F)(2) maintaining information about the second data item.
 4. The method of claim 3 where the at least some of the processing takes place in a particular device, and wherein the information maintained in (F)(2) includes information about the particular device.
 5. The method of claim 1 wherein the device is a router in a network.
 6. The method of claim 1 further comprising: obtaining a plurality of packets; and extracting payload information from the plurality of packets to obtain at least some of the second data item.
 7. The method of claim 1 further comprising: (H) in the event of a match between the first data item and the second data item, as determined in (E), subjecting the second data item to additional checking to determine if it is the same as the first data item.
 8. The method of claim 1 wherein the corresponding block of bits of each particular synch point is directly adjacent to the particular synch point.
 9. The method of claim 1 wherein said second data item comprises a stream.
 10. The method of claim 9 wherein at least one of said one or more actions associated with the first data item are selected from: (i) stopping the stream; (ii) modifying the stream; and (iii) tracking information about the stream.
 11. The method of claim 10 wherein said modifying the stream comprises: replacing at least a portion of the stream with another stream.
 12. The method of claim 11 wherein the stream is modified so that the stream's synch points and corresponding block signatures do not change.
 13. The method of claim 10 wherein said tracking information about the stream comprises tracking one or more of: date information, time information, source information, and destination information.
 14. A computer-implemented method, implemented by hardware in combination with software, the method comprising: (A) obtaining a plurality of data item signatures, at least one signature for each of a plurality of data items, the data item signature for each particular data item of the plurality of data items comprising an association between a plurality of synch points in the particular data item and a corresponding plurality of block signatures for the particular data item; (B) attempting to find a synch point of the plurality of data item signatures in a second data item; and (C) if a synch point of the plurality of data item signatures is found in the second data item, then: (C)(1) determining a block signature of a corresponding block of bits in the second data item, wherein the block signature is determined by applying a hash function or message digest function to the corresponding block of bits in the second data item; and (C)(2) ascertaining whether or not the synch point and the corresponding block signature of the second data item correspond to a synch point and block signature in any of the plurality of data item signatures; and (C)(3) when the synch point and the corresponding block signature of the second data item correspond to a synch point and block signature in one or more of the plurality of data item signatures, maintaining information indicative of the correspondence; (D) repeating steps (B) and (C) while at least some of the second data item remains unprocessed, until a predetermined number of synch points and corresponding block signatures from the second data item match synch points and corresponding block signatures in at least one of the plurality of data item signatures; (E) when a predetermined number of synch points and corresponding block signatures from the second data item match the predetermined number of synch points and block signatures in a first data item signature of the plurality of data items, indicating a match between the first data item and the second data item; and (F) in response to said determining a match in (E), performing one or more actions associated with the first data item. 